Might want to add a new test case validating the new timing fields. Maybe check that they're always positive values (or 0), and that queue time is less than completion time.

This will be a bit problematic. Because we will not create a scenario where the resources are strained and there is a queue time.

In the code it is only pulling out the values from the resource_acq table. I am sure that table will have checks in place for making sure that there are no negative values etc.

Might want to add a new test case validating the new timing fields. Maybe check that they're always positive values (or 0), and that queue time is less than completion time.

My thought is that we are pulling directly from Vertica for this data. If this test failed, it would point to an issue in Vertica, not qprof. For that reason I believe that test would be unnecessary

Looks good to me, but seems like it's failing the tests now? Or am I reading the 'Some checks were not successful' box wrong?

I did not mean to close this 😅